Include hash in parbaked recipe filename to avoid collisions #1875
+17
−5
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Contributor
|
|
daflack
approved these changes
Jan 9, 2026
Contributor
daflack
left a comment
daflack
left a comment
There was a problem hiding this comment.
Looks good to me, note I haven't run it though.
jfrost-mo
force-pushed
the
1784-avoid-recipe-collisions
branch
from
1bd8c37 to
9749347
Compare
Member
Author
|
Rebased and successfully ran through the workflow. |
jfrost-mo
temporarily deployed
to
github-pages
GitHub Actions
Inactive
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #1784 (which came from the conditions being filtered out in #1692.)
Contribution checklist
Aim to have all relevant checks ticked off before merging. See the developer's guide for more detail.